<html>
<head><meta charset="utf-8"><title>socket2 in rust-lang? · t-libs · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/index.html">t-libs</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html">socket2 in rust-lang?</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="214434834"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214434834" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214434834">(Oct 24 2020 at 16:01)</a>:</h4>
<p>Hey all! I've been the home of the <code>socket2</code> crate for some time now (<a href="https://github.com/alexcrichton/socket2-rs">https://github.com/alexcrichton/socket2-rs</a>) where the crate tries to soup up the socket support in libstd with low level configuration and an API that closely mirrors the raw berkely sockets API. I haven't been able to maintain  it for some time now but  @Thomasdezeeuw has been doing a great job. I was wondering, what would the libs team think of moving the repository into the rust-lang organization? I think it's either that or the tokio organization at this point.</p>



<a name="214447463"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214447463" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214447463">(Oct 24 2020 at 20:20)</a>:</h4>
<p>If we intend to eventually land <code>Socket</code> in std, then I think it makes sense to move into the rust-lang org. If we don't, then I think it may as well just live somewhere externally.</p>



<a name="214468713"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214468713" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214468713">(Oct 25 2020 at 04:53)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> I don't think it makes sense to use the <code>tokio</code> organization as the home for something that doesn't have a hard requirement on tokio.</p>



<a name="214468847"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214468847" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214468847">(Oct 25 2020 at 04:56)</a>:</h4>
<p>Looking over the API, I personally <em>would</em> love to see that become part of <code>std</code> someday.</p>



<a name="214477644"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214477644" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Thomas de Zeeuw <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214477644">(Oct 25 2020 at 08:37)</a>:</h4>
<p>My long term plan for socket2 is to use in std lib. First I would like to use it Mio however. This would give the entire Rust community a single crate for dealing with socket2 that would support all OS/architectures that Rust supports. But this a long term plan ~ two years. If that is too long I'm ok with keeping it as a personal repo until its ready for inclusion in std lib.</p>



<a name="214503775"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214503775" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214503775">(Oct 25 2020 at 18:13)</a>:</h4>
<p>Why does using socket2 in mio need to be a prerequisite?</p>



<a name="214503787"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214503787" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214503787">(Oct 25 2020 at 18:14)</a>:</h4>
<p>Using it in std seems orthogonal.</p>



<a name="214549228"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214549228" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Yoshua Wuyts <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214549228">(Oct 26 2020 at 09:11)</a>:</h4>
<p>Yes please, <code>socket2</code> as <code>std::net::Socket</code> in the stdlib would be incredibly useful! Pretty much every async runtime builds on some form of <code>net2</code>/<code>socket2</code> as their foundation, and setting connection flags is not great without having direct access to the socket constructor.</p>
<p>As I understand it WASI is also working on adding a BSD socket API? Exposing it from std could turn that into a nice vertical (Rust stdlib &lt;- WASI &lt;- OS BSD sockets)</p>



<a name="214597048"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214597048" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214597048">(Oct 26 2020 at 16:23)</a>:</h4>
<p>it does seem like there's some interest to move into rust-lang, so would there be any objection if I were to do that?</p>



<a name="214615665"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214615665" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Ashley Mannix <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214615665">(Oct 26 2020 at 18:36)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> Sounds great! Do you know how far off <code>socket2</code> might be from being added to <code>std</code> itself?</p>



<a name="214618236"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618236" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618236">(Oct 26 2020 at 18:57)</a>:</h4>
<p>IMO the biggest question is how to handle platform-specific settings</p>



<a name="214618298"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618298" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618298">(Oct 26 2020 at 18:57)</a>:</h4>
<p>extension traits are the "traditional" way, but they're really kind of gross, so I'm wondering how things would go if we just add cfg'd methods now that rustdoc has support to display the cfg's required for a specific bit of API</p>



<a name="214618412"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618412" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618412">(Oct 26 2020 at 18:58)</a>:</h4>
<p>the atomics already do that. and with cfg(accessible) it might become more common</p>



<a name="214618456"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618456" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618456">(Oct 26 2020 at 18:59)</a>:</h4>
<p>yeah</p>



<a name="214618487"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618487" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618487">(Oct 26 2020 at 18:59)</a>:</h4>
<p>and this seems like a less risky place to try it out since Socket is a quite low-level API</p>



<a name="214618493"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618493" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618493">(Oct 26 2020 at 18:59)</a>:</h4>
<p>I think on a type like Socket which has almost all APIs otherwise behind extension traits it makes sense</p>



<a name="214618501"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618501" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618501">(Oct 26 2020 at 18:59)</a>:</h4>
<p>where presumably you'd have a better idea of just how platform specific you're being</p>



<a name="214618517"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214618517" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214618517">(Oct 26 2020 at 18:59)</a>:</h4>
<p>yeah</p>



<a name="214642031"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214642031" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214642031">(Oct 26 2020 at 22:39)</a>:</h4>
<p><span class="user-mention" data-user-id="204346">@Ashley Mannix</span> tbh I haven't followed the crate a ton recently and it's recently gone through a number of changes so I'm not sure.</p>



<a name="214642036"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214642036" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214642036">(Oct 26 2020 at 22:39)</a>:</h4>
<p>where I left it I wouldn't consider it too far from adding to std itself</p>



<a name="214642265"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214642265" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214642265">(Oct 26 2020 at 22:42)</a>:</h4>
<p>ok I'll plan to move the repo soon unless anyone feels otherwise in the next few days</p>



<a name="214648729"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214648729" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214648729">(Oct 27 2020 at 00:18)</a>:</h4>
<p><span class="user-mention silent" data-user-id="243558">Steven Fackler</span> <a href="#narrow/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F/near/214618298">said</a>:</p>
<blockquote>
<p>extension traits are the "traditional" way, but they're really kind of gross, so I'm wondering how things would go if we just add cfg'd methods now that rustdoc has support to display the cfg's required for a specific bit of API</p>
</blockquote>
<p>small note, rustdoc has had this support for a while, the only thing that changed recently is it now works for <code>impl Trait</code></p>



<a name="214648759"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214648759" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214648759">(Oct 27 2020 at 00:19)</a>:</h4>
<p><a href="https://doc.rust-lang.org/nightly/rustdoc/advanced-features.html#interactions-between-platform-specific-docs">https://doc.rust-lang.org/nightly/rustdoc/advanced-features.html#interactions-between-platform-specific-docs</a></p>



<a name="214804550"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214804550" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214804550">(Oct 28 2020 at 07:59)</a>:</h4>
<p>Side note, is there any fundamental reason we couldn't move existing extension trait methods into the types they extend?</p>



<a name="214823062"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214823062" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214823062">(Oct 28 2020 at 11:24)</a>:</h4>
<p>No - the traits are only there to force people to explicitly import them as a kind of speedbump to accidentally writing platform-dependent code</p>



<a name="214823099"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214823099" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214823099">(Oct 28 2020 at 11:24)</a>:</h4>
<p>The portability lint was designed to act as that, but it's not clear that it's ever actually going to happen</p>



<a name="214889406"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214889406" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214889406">(Oct 28 2020 at 19:57)</a>:</h4>
<p><span class="user-mention" data-user-id="243558">@Steven Fackler</span> I'm not sure that's worth the corresponding hassle. I <em>do</em> want to see the portability lint happen, and I'd love to see someone pick that up and run with it, but I don't think that <em>should</em> be a prerequisite to simplifying target-specific methods to just be <code>cfg</code>-controlled.</p>



<a name="214889540"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214889540" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214889540">(Oct 28 2020 at 19:58)</a>:</h4>
<p>Yeah I don't think it's a hard prereq either</p>



<a name="214916209"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214916209" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nagisa <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214916209">(Oct 29 2020 at 01:06)</a>:</h4>
<p>I don't share that opinion at all. Being able to see that the code is platform specific in code review has been critical to keeping codebases properly portable.</p>



<a name="214916281"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214916281" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nagisa <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214916281">(Oct 29 2020 at 01:07)</a>:</h4>
<p>I don't particularly care if its an import or a lint or something else entirely as long as its obvious from looking at the code that e.g. <code>(x: &amp;OsStr).as_bytes()</code> is not portable.</p>



<a name="214930462"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214930462" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214930462">(Oct 29 2020 at 06:26)</a>:</h4>
<p>I'd definitely like to have the portability lint, along with the ability to easily assert somewhere at the top of the code "this is target X, don't warn about anything that works on target X".</p>



<a name="214930497"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214930497" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214930497">(Oct 29 2020 at 06:27)</a>:</h4>
<p>But the extension traits are a painful way of handling that. Leaving aside the splits in the code, and the separate imports, they're also hard to extend without causing breakage, and require the careful "sealed trait" dance, which people can and do forget when adding new ones.</p>



<a name="214930627"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214930627" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214930627">(Oct 29 2020 at 06:30)</a>:</h4>
<p>They also require a separate trait for any given variation in targets (e.g. one extension trait for unix and another one for linux), which introduces substantial friction when introducing support for calling some platform's functions.</p>



<a name="214930638"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214930638" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Josh Triplett <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214930638">(Oct 29 2020 at 06:31)</a>:</h4>
<p>I think there's quite a bit of value in eliminating that in favor of the standard <code>cfg</code> mechanism.</p>



<a name="214965373"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/214965373" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Joshua Nelson <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#214965373">(Oct 29 2020 at 13:25)</a>:</h4>
<p>/me glances at <a href="https://github.com/rust-lang/rust/issues/77089">https://github.com/rust-lang/rust/issues/77089</a></p>



<a name="215017728"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215017728" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215017728">(Oct 29 2020 at 19:40)</a>:</h4>
<p>ok repo moved! <a href="https://github.com/rust-lang/socket2-rs">https://github.com/rust-lang/socket2-rs</a></p>



<a name="215017855"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215017855" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215017855">(Oct 29 2020 at 19:41)</a>:</h4>
<p>Do the same maintainer(s) still have write access?</p>



<a name="215085686"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215085686" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215085686">(Oct 30 2020 at 12:11)</a>:</h4>
<p>It got a new PR just now. Is there anyone right now who can actually review and merge things on this repository, now that it's moved? Not sure where to look exactly, but I think nobody has write access to it right now.</p>



<a name="215088502"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215088502" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215088502">(Oct 30 2020 at 12:39)</a>:</h4>
<p>@Thomasdezeeuw and @stjepang are both admins on the repo according to the manage access page</p>



<a name="215095352"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215095352" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215095352">(Oct 30 2020 at 13:41)</a>:</h4>
<p>Ah okay, cool :)</p>



<a name="215693607"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215693607" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Thomas de Zeeuw <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215693607">(Nov 05 2020 at 10:29)</a>:</h4>
<p>@stjepang unfortunately doesn't have enough time to maintain socket2 any more. I'm quite busy this month still, but after that should have enough time for socket2. I would however like someone to review with me, especially the prs I intend to send</p>



<a name="215695153"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/socket2%20in%20rust-lang%3F/near/215695153" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Mara <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/socket2.20in.20rust-lang.3F.html#215695153">(Nov 05 2020 at 10:44)</a>:</h4>
<p>I wouldn't mind helping out with reviews there, if that helps. But maybe some of the existing contriutors want to help maintain socket2? Looks like <code>de-vri-es</code> has been somewhat active lately.</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>